System and method for conveyor maintenance

ABSTRACT

Systems and methods are provided for conveyor operation and maintenance that employ a “smart shoe” technology where one or more conveyor shoes incorporate features, such as an RFID tag, allowing selective wireless tracking and identification capability. A conveyor system comprises a shoe management system allowing interactions directly with a reader where interface between this application and the reader can be implemented via a socket interface. An open platform communications (OPC) wrapper can be created around the interface so that a Human Machine Interface (HMI) could interact directly with shoe management system

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to prior U.S. Provisional PatentApplication No. 62/555,061, filed Sep. 7, 2017, the entire content ofwhich is incorporated herein by reference.

BACKGROUND 1. Field of Disclosure

Generally, exemplary embodiments of the present disclosure relate to thefield of conveyors and conveyor operation, and more particularlysortation conveyor systems including sliding shoe sorters. Exemplaryimplementations of certain embodiments of the present disclosure providea system and method allowing missing shoe detection, identificationand/or correction during conveyor operation.

2. Background of Disclosure

During operation of sliding shoe sorters deployed in conventionalconveyor systems (such as those including a conveyor 300 generallyillustrated in FIG. 3), conveyor shoes (such as shoes 400 generallyillustrated in FIG. 4), may become dislodged from the conveyor andtimely detection of such an occurrence can be challenging, resulting inmishandling of packages, and in some cases breakdowns, halting operationfor significant amount of time.

SUMMARY

Exemplary embodiments of the present disclosure address at least suchdrawbacks by providing systems and methods that employ a “smart shoe”technology where one or more shoes incorporate features allowingselective wireless tracking and identification capability, and provideat least the advantages described below.

According to one aspect of the present disclosure there is provided aconveyor shoe that includes: a housing; a circuit including a radiofrequency transceiver transmitting information uniquely associated withthe shoe; and a mechanism securing the circuit with respect to thehousing.

According to an exemplary implementation, the circuit including a radiofrequency transceiver transmitting information uniquely associated withthe shoe comprises radio frequency identification (RFID) tag.

Optionally, in any of the preceding aspects the mechanism securing thecircuit with respect to the housing provides secure attachment of thecircuit with respect to the housing to maintain the attachment duringoperation of the shoe.

Optionally, in any of the preceding aspects the mechanism securing thecircuit with respect to the housing comprises a cavity within saidhousing removably securing said RFID tag therein.

Optionally, in any of the preceding aspects the RFID tag selectivelyestablishes communication with an RFID reader providing the RFID readerinformation uniquely associated with the shoe.

According to another aspect of the present disclosure there is provideda system that includes: a conveyor; at least one conveyor shoecomprising one or more, in any combination, of the preceding aspects;and at least one reader selectively establishing communication with thecircuit of the at least one shoe.

According to an exemplary implementation, the system can further includea user interface in wired or wireless communication with the at leastone reader selectively receiving, processing, storing, and/or displayingthe information uniquely associated with the at least one conveyor shoe.

Optionally, in any of the preceding aspects, the system includes aplurality of the conveyor shoes each including the circuit transmittinginformation uniquely associated with the conveyor shoe.

Optionally, in any of the preceding aspects, the system including a userinterface can be configured such that the user interface selectivelycontrols operation of the conveyor based on the information uniquelyassociated with at least one of the plurality of conveyor shoes.

According to another aspect of the present disclosure there is provideda method including: deploying on a conveyor at least one conveyor shoecomprising one or more, in any combination, of the preceding aspects;and selectively establishing communication between at least one readerand the circuit of at least one conveyor shoe.

According to an exemplary implementation, the method can further includeselectively establishing wired or wireless communication between a userinterface and at least one reader; and selectively receiving,processing, storing, and/or displaying said information uniquelyassociated with at least one conveyor shoe via the user interface.

Optionally, in any of the preceding aspects, the method includesdeploying on the conveyor a plurality of conveyor shoes each includingthe circuit transmitting information uniquely associated with theconveyor shoe.

Optionally, in any of the preceding aspects, the method includesselectively controlling operation of the conveyor via a user interfacebased on the information uniquely associated with at least one of theplurality of conveyor shoes.

Optionally, in any of the preceding aspects, the method includesautonomously controlling operation of the conveyor, for example via auser interface, based on the information uniquely associated with atleast one of the plurality of conveyor shoes.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, advantages and salient features of thedisclosure will become apparent to those skilled in the art from thefollowing detailed description of illustrative embodiments thereof whentaken in conjunction with the accompanying drawings in which:

FIG. 1 illustrates an example of a conveyor shoe according toembodiments of present disclosure.

FIG. 2 illustrates an example of another view of a conveyor shoeaccording to embodiments of present disclosure.

FIG. 3 illustrates an example of a conventional conveyor.

FIG. 4 illustrates an example of conventional conveyor shoes.

FIG. 5 is a diagrammatic illustration of an example of a systemaccording to embodiments of present disclosure.

FIG. 6 is another diagrammatic illustration of an example of a systemaccording to embodiments of present disclosure.

FIG. 7 is a diagrammatic illustration of an example of an operation of asystem according to embodiments of present disclosure.

FIGS. 8-11 are diagrammatic illustrations of an example of a methodusing a system configuration according to embodiments of presentdisclosure.

FIG. 12 is a diagrammatic illustration of another example of anoperation of a system according to embodiments of present disclosure.

FIG. 13 is a diagrammatic illustration of an example of an operation ofa system according to embodiments of present disclosure.

FIG. 14 is another diagrammatic illustration of an example of a systemaccording to embodiments of present disclosure.

FIG. 15 is a diagrammatic illustration of an example of an operationincluding software and hardware components of a system according toembodiments of present disclosure.

FIG. 16 illustrates another example of a conveyor shoe according toembodiments of present disclosure.

FIG. 17 is a diagrammatic illustration of an example of a configurationof hardware components of a system according to embodiments of presentdisclosure.

FIG. 18 is a diagrammatic illustration of another example of aconfiguration of hardware components of a system according toembodiments of present disclosure.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The matters exemplified in this description are provided to assist in acomprehensive understanding of exemplary embodiments of the disclosure.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the embodiments described hereincan be made without departing from the scope and spirit of the disclosedembodiments. Also, descriptions of well-known functions andconstructions are omitted for clarity and conciseness

An exemplary embodiment of the present disclosure employing “smart shoe”technology provides at least one shoe including a radio frequencyidentification (RFID) tag allowing the at least one shoe to be uniquelyidentified by a reader, which can be an RFID reader capable ofcommunicating with the RFID tag.

Another exemplary embodiment of the present disclosure employing “smartshoe” technology provides a conveyor system including a plurality of, orall, shoes each including a radio frequency identification (RFID) tagallowing each of the shoes to be uniquely identified and monitored by atleast one reader deployed by the conveyor system to provide real timeand/or historical data indicative of the operation of each shoe and/orthe conveyor system.

Yet another exemplary embodiment of the present disclosure employing“smart shoe” technology provides a conveyor system including a pluralityof, or all, shoes each including a radio frequency identification (RFID)tag allowing each of the shoes to be uniquely identified by at least onereader deployed by the conveyor system, whereby operation of theconveyor system can be controlled by a user, our autonomouslycontrolled, based on real time and/or historical data indicative of theoperation of each shoe and/or the conveyor system provided by thereader(s).

In a non-limiting exemplary implementation of exemplary embodiments ofthe present disclosure, diagrammatically shown in the examples of FIGS.1 and 2, a smart shoe 100 disposed on a sliding assembly 130 comprises ahousing 102 including an RFID tag 200 therein. As illustrated, housing102 can include a slot or compartment 124 for accommodating a tray 112for an RFID tag 200 such that, once RFID tag 200 is placed in the tray112, the tray 112 can be secured in the slot or compartment 124, forexample by means of one or more screws 116 and nuts 118 attaching one ormore portions 120 of tray 112 to housing 102. In yet further exemplaryimplementation, housing 102 includes one or more mounting areas, such asholes 126, 128, for mounting housing 102 to slat 104. Pin components106, 108 are connected to slat 104 via a mounting bracket 110.

While a detailed implementation is described with reference to FIGS. 1and 2, any means of attaching or incorporating an RFID tag in or on ashoe of a conveyor system is within the scope of the present disclosure.

Another exemplary embodiment of the present disclosure provides aconveyor system including one or more shoes, preferably all shoes,having an RFID tag associated therewith, for example as described abovewith reference to FIGS. 1 and 2, and at least one RFID tag reader.According to an exemplary implementation, a conveyor system comprises ashoe management system allowing customer interactions directly with thereader where, for example, interface between this application and thereader can be implemented via a socket interface. In a further exemplaryimplementation, an OPC (open platform communications) wrapper can becreated around the interface so that a HMI (Human Machine Interface)could interact directly with the shoe management system.

An exemplary embodiment of the present disclosure provides a system andmethod for monitoring a conveyor operation deploying shoes with RFIDtags, configured for example as described with reference to FIGS. 1 and2, facilitating accurate detection and identification of a missing shoesuch as when a shoe comes off of the conveyor using communicationbetween shoe's RFID tag and at least one RFID reader strategicallydeployed with respect to the conveyor and/or the shoes, andcommunication between the at least one reader and a system, such as aportable computer, a hand-held communication device, a server, andInternet-based solution, etc., providing a user interface, and/or aprogrammable logic controller (PLC). In an exemplary implementation,communication to the PLC can be supported using any available protocols,such as Ethernet Industrial Protocol (EIP) and/or Transmission ControlProtocol/Internet Protocol (TCP/IP) adaptable to the hardware of RFIDreader.

In an exemplary implementation, system and method according to exemplaryembodiments of the present disclosure provide various modes of operationfor a conveyor system implementing smart shoe technology includingwithout limitation: commissioning and setup mode where at least onereader is determining what RFID tag(s) are in any one or more of therespective shoes; operational mode where a sorter conveyor is running atand operational speed and at least one reader is actively monitoring thestatus of one or more of RFID tag carrying shoes on the sorter;maintenance mode where a PLC can request to be notified when aparticular shoe is at the reader and the reader can respond by sending ashoe status notification such that the PLC can properly present the shoein a maintenance area; and/or broken shoe presentation mode where anidentified broken shoe can be present to a maintenance area by a sorter.

Exemplary non-limiting implementations of various operation modesprovided by the system and methods of the exemplary embodiment of thepresent disclosure deploying “smart shoe” technology are described asfollows.

Referring to FIGS. 5-7, according to exemplary implementations, amissing-shoe detection system with an added RFID component optionallycan be deployed on an existing conveyor product line to provide, withoutlimitation and in any combination:

Missing Shoe Detection and Correction:

During conveyor operation, automatically identifying missing ‘sortshoes’ on the conveyor 500, and sending a message, for example to aconveyor maintenance station 510, to set the conveyer to “missing-shoemaintenance” mode. From missing-shoe maintenance mode, a series ofcorrective steps will be followed by the operator to replace that shoe.

Sectional-Identification During ‘Non-Shoe Related’ Conveyor MaintenanceCycles:

Using the RFID tags on the sort-shoes, such as those described abovewith reference to FIGS. 1 and 2, to identify “already completed”sections 520, 521, 522, 523, 524 of the conveyor 500 during traditional(non-shoe related) conveyor maintenance cycles.

Cycle-Count Record Keeping of Sort-Shoes:

For preventative maintenance purposes, the system can keep track of thenumber of times shoes 650, 660 rotate around the conveyor 600. Asindividual shoes get replaced during the “missing shoe detection andcorrection” process those shoes will be decommissioned by the system,while the new (replacement) shoes will be introduced and will begintheir own cycle-count records.

Exemplary Implementation:

If the missing shoe identification and replacement feature is notdesired, cycle-count read capability only can be implemented using oneRFID read point, which translates to 1 reader×2 antennas.

RFID-System Commissioning and RFID Setup Procedure:

Every newly-deployed conveyor 600 can be fitted with sort-shoes thathave RFID tags, for example shoe 660 including any combinations offeatures described above with reference to FIGS. 1 and 2 fitted with atag 702. When the conveyor-system is initially turned on and/or is putinto commissioning or setup mode the RFID reader 630 and/or 640 at oneof two designated read points can begin programming these RFID tags oneat a time. Once all of the tags have moved through the encoding cycle670, the RFID-component of the conveyor system can be deemed “ready foruse”.

Exemplary Detailed Implementations

-   -   The RFID system can encode these tags 702 in numeric-sequential        order, and know when the encoding cycle is complete upon reading        the first tag it programmed at the onset of this process.    -   If, during the RFID-tag encoding process a tag is missed (not        programmed), this will be detected by the system during an        ensuing conveyor-run cycle, and the system will prompt the        operator to run the encoding cycle again.    -   As each shoe-tag is encoded during the setup cycle 770, that        tag's RFID EPC number will be logged into a database 700. From        that point forward, that shoe will be individually identified by        that EPC number.

[FIG. 8-13]

Referring to FIGS. 8-13, exemplary implementations provide optionallyand/or in combination with other features, a Missing Shoe Detection andCycle Counts as follows. As the conveyor 800 runs, every shoe's RFID tagis recorded as having completed one full cycle each time it passes bythe RFID read point. If a particular tag does not pass by the RFIDread-point after a given number of cycle runs (i.e., the “number ofruns” it takes to determine that a shoe is missing can be set on asituational basis), that tag (i.e., that shoe) is deemed by the systemas being missing. Consequently, the system sends an alert and goes into“missing shoe” recovery mode. During Missing Shoe Recovery Mode, theoperator can by-pass or accept the alert, and upon accepting the alertthe conveyor automatically slows down to ⅕ speed (i.e., down to 120 fpmfrom 600 fpm) allowing the operator to then search for the missing shoe.

As the operator searches for the missing shoe from atop the conveyors'maintenance station/platform, he puts the conveyor into “jog” mode. Theoperator has the benefit of knowing precisely where the ‘missing-shoebearing’ is on the conveyor and when it will arrive at the maintenancestation, as during the RFID setup process all of the RFID tags weresequentially numbered.

Exemplary implementation can be described with reference to FIGS. 8-11as follows:

-   -   Step 1 (FIG. 8): Bearing with missing shoe passes by two        read-points 810 and 820, and system deems that shoe as missing.    -   Step 2 (FIG. 9): Upon operator accepting alert, conveyor slows        down, for example to ⅕ speed (120 ft. per minute).    -   Step 3 (FIG. 10): Upon honing in on “missing shoe bearing” area        850, the operator puts conveyor into “jog” mode to isolate that        bearing.    -   Step 4 (FIG. 11): Operator finds missing-shoe bearing by honing        in on RFID tags 805 and 803 that were directly in front of the        missing shoe 804.

Referring to FIG. 12, an exemplary implementation of Replacement-TagEncoding includes: after a missing shoe gets physically replaced on theconveyor, it is critical that the RFID tag of replacement shoes 1216 isencoded, for example via reader/encoder 1220 in such a way that thatparticular shoe is identified by the system in the correct physicalsequence. Associated steps are as follows:

-   -   a. Shoe 1216 is physically placed on bearing of conveyor 1200    -   b. Operator puts system into tag re-encoding mode and conveyor        begins cycling in search of ‘newly replaced’ RFID tag. The        system knows which tag to re-encode by scanning and identifying        the tags of shoes such as 1210, 1212, 1214 directly in front of        it on the conveyor 1200. The system also knows what EPC number        to encode the replacement-tag with, so that the replacement-tag        is always recognized by the system in the correct sequence (for        jogging, etc.).    -   c. Replacement-tag is encoded, with the same EPC number as the        original tag it replaced—plus one bit-change at the end of the        EPC that identifies that tag as being associated to a        “replacement” shoe.

Exemplary Implementation:

The entire process above can be circumvented at any point in timethrough a manual-override option on the conveyor console, so that thedecision of when to replace the missing shoe can be made by theoperator.

Referring to FIG. 13, exemplary implementations provide a Non-ShoeRelated ‘Conveyor Maintenance Mode’ where for example conveyor 1300 issectionalized, with each section 1301, 1302, 1302, 1304, 1306, 1307,1308 being identified by those RFID tags that reside within it. Duringtraditional maintenance cycles (i.e. non-RFID related, incrementalconveyor maintenance) the operator (conveyor maintenance station 1350)has the ability to jog the conveyor by individual sections, servicethose sections, and consequently identify/categorize those sectionswithin the system as either having been completed (for example, section1301, 1302, 1306, 1307, 1308) for service, in progress (for example,section 1305), or still needing to be serviced (for example, sections1303 and 1304).

Referring to FIG. 14, exemplary implementations provide hardwareincluding, without limitation and in any combination: two RFID readstations 1440, 1450, one at each end of the sortation conveyor 1400. Anystation or all stations, such as stations 1440, 1450 can comprise areader 1446 and for example tow antennas 1442, 1443, covering the left1406 and right 1408 of the belt 1404 in order to capture shoes that canbe either left or right justified. The readers can be inside, forexample a NEMA 1 rated, enclosure 1449, and the antennas can be mounteddirectly underneath the belt 1404. In an exemplary implementation, bothstations 1440, 1450 can read tags, but only “Station 1” 1440 can beconfigured to handle the encoding processes. For example, a PC 1448 canbe installed within enclosure 1449 of station 1440, but can connect andcommunicate with readers in both stations 1440, 1450.

Referring to FIG. 15, which diagrammatically illustrates an RFIDsoftware stack 1500 according to an exemplary implementation, where anexample of RFID Software Requirements include the following:

Functional User-Interface Requirements

-   -   a. UI for putting conveyor into commissioning mode    -   b. UIs for alert-notification for when conveyor goes into        “missing shoe identification and recovery” mode    -   c. UI for switching conveyor from “missing shoe and recovery”        mode to “replacement-tag programming” mode    -   d. UI for switching conveyor from replacement-tag programming        mode to “regular operation” mode    -   e. UI layer for RFID-system remote-access troubleshooting        -   i. Reader ‘On Line” verification        -   ii. Reader Reboot        -   iii. Reader Settings pushout (manual step)        -   iv. Antenna-Port verification        -   v. Firmware Upgrade capability        -   vi. Settings Check (Selected Settings)    -   f. UI layer for RFID-system on-site operations        -   i. See items a through d above

2) Infrastructure and Engine-Logic Requirements:

-   -   g. Static Database to store system-setup and configuration        information (Tag identification association, etc.)    -   h. Dynamic Database for tag-read recording    -   i. System Setup Engine—To sequentially encode tags, log those        tags into the static database, and maintain the knowledge of how        (in which order) those tags are physically lined up on the        conveyor    -   j. ‘Missing Tag’ Recovery Mode—Logic to conclude that a tag        (shoe) is missing from having passed through two read points        without being detected, to automatically put the conveyor into        slowdown mode (⅕ speed) as a result of a tag being deemed as        missing, and finally, to send alerts    -   k. Reprogramming/Tag-Replacement Mode—Logic to identify which        tag needs to be programmed (by identifying the tag in front of        it, and/or by recognizing the EPC as having an E200 prefix),        logic to automatically program the replacement tag with the same        EPC as its' predecessor tag—but with one added bit at the end        for “replacement v. original” tag identification    -   l. Cycle Counts—The ability to count the number of times a        shoe-tag travels through the conveyor checkpoints    -   m. Logic for conveyor-section identification through tag-ID        association    -   n. Software Layer for remote-access troubleshooting (refer to        bullet-point “e” in “functional user-interface requirements”        section, above)    -   o. Software Layer for on-site system operations (see        bullet-points a through d in “functional user-interface        requirements” section, above)

An exemplary implementation of RFID Tag Selection, Tag Placement and TagEncoding are describes as follows:

Tag Selection: Any RFID tag can be implemented according to thedisclosure. For example, a tag selected for this application can be aconventional RFID tag such as ALN-9830 manufactured by Alien TechnologyLLC. This tag measuring 70 mm×9.5 mm can fit within the molded shoe. Theshape and orientation of the inlay can facilitate rapid, close proximityreading. However, other RFID design may also be used based on desiredimplementation and testing.

Tag Placement: as described in the examples of FIGS. 1 and 2 above, andfurther illustrated in FIG. 16, a tag can be inserted into the shoe 1600during the injection molding process. It can be oriented such that thetag is parallel to the conveyor slat 1602.

Tag Encoding: As the RFID system can be encoded using a full 96 bit EPCbank in any manner. In an exemplary implementation, one of the bits canbe used to identify that a shoe is a replacement shoe, in order for thesystem to know to start a new count of cycles for that shoe.

Referring to the examples of FIGS. 17 and 18, hardware design optionsimplementing embodiments of the present disclosure using varioushardware components, such as those manufactured by Alien Technology LLC.

An example of a fixed reader configuration is illustrated in FIG. 17where an all RFID Solution-Software can reside in a huh unit 1750 andinclude:

-   -   Reader Firmware    -   Middleware    -   Databases (static and dynamic)    -   Event-Control Engine    -   Process-Logic Engine    -   Software-Layer for all local RFID operation    -   Software-Layer for all remote-access troubleshooting    -   User Interfaces

In an exemplary implementation (see also FIG. 14) hub unit 1750 andspoke unit 1755 can include an RFID reader and be connected torespective antennas 1751, 1752 and 1756, 1757. Hub unit 1750 and spokeunit 1755 can be interconnected via an Ethernet component 1780 withconveyor engine 1790.

An example of a module configuration is illustrated in FIG. 18 where anall RFID Solution-Software can reside in one or more connected computingdevices 1850, 1860 including a microprocessor and a non-transitorycomputer-readable storage medium including storage ofcomputer-executable instructions, and can include:

-   -   Reader Firmware    -   Middleware    -   Databases (static and dynamic)    -   Event-Control Engine    -   Process-Logic Engine    -   Software-Layer for all local RFID operation    -   Software-Layer for all remote-access troubleshooting    -   User Interfaces

In an exemplary implementation (see also FIGS. 14 and 17) computingdevices 1850 can be connected in a wired or wireless configuration withrespective modules 1852, 1862 that can include an RFID reader and beconnected to respective antennas 1853, 1854 and 1863, 1864. Modules1852, 1862 can be interconnected via an Ethernet component 1880 withconveyor engine 1990.

A further exemplary implementations of the embodiment of the presentdisclosure provide for reader data collection where a user device incommunication with the reader, or the reader itself can store, forexample in a file format, a list of all the valid RFIDs values for thesorter, such that upon startup, the file can be read, and for example ifa file is not found or cannot be read, an error will be reported. In yetfurther exemplary implementation, every command received by the PLC canbe stored, for example in a file/folder format by date, such that forexample on a rolling basis, a particular period (e.g., 1 month) orrecords can be store and made available. In still further exemplaryimplementation items recorded can include without limitation any of:

-   -   Power On Events    -   Command Events    -   Record the detection of missing shoes    -   Maintenance Mode usage        and/or shoe data can include for each shoe (for example at a        minimum):    -   Number of revolutions since each particular shoe was ‘read’ by        the scanner    -   Time Stamp for the last time a shoe was ‘read’.

According to further exemplary implementations of the embodiment of thepresent disclosure the following non-limiting interface examplesinclude:

PLC to Reader

INT[X] Definition 1 Heartbeat. Value incrementing every second willincrement from 1 to 1000 2 Speed of Sorter in FPM. 3 Command 1 = PresentShoe 2 = Setup Mode 3 = Broken Shoe 4 = Regular Run 5 = Request Data 4Shoe Number to Present/Request Data 5 Number Of Shoes On Sorter

Reader to PLC

INT[X] Definition 1 Heartbeat. Value incrementing every second willincrement from 1 to 1000 2 Last Shoe Read 3 Status: 1 = Presenting Shoe2 = In Setup Mode 3 = Broken Shoe Detected 4 = In Regular Run 5 =Requested Data 4 ID of First Broken Shoes 5 Number Of Broken Shoes 6Request Shoe 7 Requested Shoe OK 8 Requested Shoe Read Counts 9 LastSeen 1 = Right Side 2 = Left Side 10 Last Seen 1 = induct 2 = discharge

While the present disclosure has been shown and described with referenceto certain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the presentdisclosure. For example, various communication protocols can be deployedwith various RFID tag and RFID reader hardware, and/or various visualand/or audio user interfaces can be implemented to facilitate processingand/or displaying information and/or controlling hardware and/orsoftware components of the system.

In addition, the drawing figures that follow further describenon-limiting examples of implementations of certain exemplaryembodiments of the present disclosure and aid in the description oftechnology associated therewith.

Thus, the description and figures are intended by way of example onlyand are not intended to limit the illustrative embodiments in any wayexcept as set forth in the appended claims and their full scope ofequivalents. Also, various technical aspects of the various elements ofthe various exemplary embodiments that have been described above can becombined in numerous other ways, all of which are considered to bewithin the scope of the disclosure.

1.-12. (canceled)
 13. A shoe of a conveyor system, the shoe comprising:a housing; a pin component; and at least one radio frequency transceiversecured with respect to the housing.
 14. The shoe of claim 13, whereinthe radio frequency transceiver comprises a radio frequencyidentification (RFID) tag.
 15. The shoe of claim 13, wherein: the atleast one radio frequency transceiver is configured to transmitinformation uniquely associated with the shoe.
 16. The shoe of claim 15,wherein the radio frequency transceiver is removeably secured to thehousing.
 17. The shoe of claim 15, wherein the housing comprises a slotformed therein and a tray configured to be secured within the slot andto bold the radio frequency transmitter therewithin.
 18. The shoe ofclaim 13, wherein the pin component is secured to the housing andcomprises a pin and a roller.
 19. A conveyor system comprising: aconveyor frame; at least one slat disposed on the conveyor frame; atleast one shoe disposed on the at least one slat, the shoe comprising ahousing, a pin component, and at least one radio frequency transceiversecured with respect to the housing; and a read station configured toestablish communication with the radio frequency transceiver.
 20. Theconveyor system of claim 19 comprising a plurality of slats includingthe at least one slat and a plurality of shoes respectivelycorresponding to the plurality of slats including the at least one shoe.21. The conveyor system of claim 19, wherein: the conveyor frame forms aclosed loop; and the read station comprises a first read station,disposed at a first side of the closed loop and a second read station,disposed at a second side of the closed loop, substantially opposite thefirst side.
 22. The conveyor system of claim 19, wherein the radiofrequency transceiver comprises a radio frequency identification (RFID)tag.
 23. The conveyor system of claim 19, wherein the at least one radiofrequency transceiver is configured to transmit information uniquelyassociated with the shoe.
 24. The conveyor system of claim 19, whereinthe pin component is secured to the housing and comprises a pin and aroller
 25. The conveyor system of claim 19, further comprising: anexternal device; wherein the at least one read station is configured totransmit information regarding the at least one shoe to the externaldevice.
 26. The conveyor system of claim 25, wherein the external devicecomprises at least one of a portable computer, a hand-held communicationdevice, and a server.
 27. The conveyor system of claim 25, wherein theexternal device comprises a user interface.
 28. The conveyor system ofclaim 25, wherein the information regarding the at least one shoecomprises information identifying that the shoe is missing.
 29. Theconveyor system of claim 25, wherein the information regarding the shoecomprises a number of times the at least one shoe has completed a cycleof the conveyor system.
 30. A method of operation of a conveyor, themethod comprising: conveying, along a conveyor frame, a shoe comprisinga housing, a pin component, and at least one radio frequency transceiversecured to the housing; the at least one radio frequency transceivertransmitting identification information uniquely identifying the shoe;and a read station establishing communication with the at least oneradio frequency transceiver and receiving the identificationinformation.
 31. The method of claim 30, further comprising the readstation transmitting the identification information to a user interface.32. The method of claim 30, further comprising autonomously controllingoperation of the conveyor based on the identification information. 33.The method of claim 30, wherein the read station establishingcommunication comprises a first read station and a second read stationeach establishing communication with the at least one radio frequencytransceiver and receiving the identification information.